Verifying and Saving Your Configuration

Verifying and Saving Your Configuration
 
 
This chapter describes how to save your system configuration.
 
Verifying the Configuration
You can use a number of commands to verify the configuration of your feature, service, or system. Many are hierarchical in their implementation and some are specific to portions of, or specific lines in, the configuration file.
 
Feature Configuration
In many configurations, you have to set and verify specific features. An example includes IP address pool configuration. Using this example, enter the following commands to verify proper feature configuration:
Enter the following command to display the IP address pool configuration:
show ip pool
The output from this command should look similar to the sample shown below. In this example, all IP pools were configured in the isp1 context.
context : isp1:
+-----Type: (P) - Public (R) - Private
| (S) - Static (E) - Resource
|
|+----State: (G) - Good (D) - Pending Delete (R)-Resizing
||
||++--Priority: 0..10 (Highest (0) .. Lowest (10))
||||
||||+-Busyout: (B) - Busyout configured
|||| |||||| vvvvv Pool Name Start Address Mask/End Address Used Avail
----- --------- --------------- --------------- -------- --------
PG00 ipsec 12.12.12.0 255.255.255.0 0 254 PG00
pool1 10.10.0.0 255.255.0.0 0 65534 SG00
vpnpool 192.168.1.250 192.168.1.254 0 5 Total Pool Count: 5
note_smallImportant: To configure features on the system, use the show commands specifically for these features. Refer to the Cisco Systems ASR 5000 Command Line Interface Reference for more information.
 
Service Configuration
Verify that your service was created and configured properly by entering the following command:
show <service_type> <service_name>
The output is a concise listing of the service parameter settings similar to the sample displayed below. In this example, a P-GW service called pgw is configured.
Service name : pgw1
Service-Id : 1
Context : test1
Status : STARTED
Restart Counter : 8
EGTP Service : egtp1
LMA Service : Not defined
Session-Delete-Delay Timer : Enabled
Session-Delete-Delay timeout : 10000(msecs)
PLMN ID List : MCC: 100, MNC: 99
Newcall Policy : None
 
Context Configuration
Verify that your context was created and configured properly by entering the following command:
show context name <name>
The output shows the active context. Its ID is similar to the sample displayed below. In this example, a context named test1 is configured.
Context Name     ContextID     State
------------     ---------     -----
test1            2          Active
 
System Configuration
Verify that your entire configuration file was created and configured properly by entering the following command:
show configuration
This command displays the entire configuration including the context and service configurations defined above.
 
Finding Configuration Errors
Identify errors in your configuration file by entering the following command:
show configuration errors
This command displays errors it finds within the configuration. For example, if you have created a service named “service1”, but entered it as “srv1” in another part of the configuration, the system displays this error.
You must refine this command to specify particular sections of the configuration. Add the section keyword and choose a section from the help menu:
show configuration errors section ggsn-service
or
show configuration errors section aaa-config
If the configuration contains no errors, an output similar to the following is displayed:
################################################################################
Displaying Global
AAA-configuration errors ################################################################################
Total 0 error(s) in this section !
 
Saving the Configuration
Save system configuration information to a file locally or to a remote node on the network.
Caution_iconCaution: Prior to loading 12.2, we recommend that copies of the original configuration file be made and stored (with unique release-identifying titles) both in the Flash and off the chassis. Configuration files created and saved in release 12.2 cannot be shared across multiple chassis due to a change in the encryption algorithm for passwords and secrets. These 12.2 changes modify encrypted data in the configuration file so that it cannot be recognized by previous software builds. If it is necessary to revert to a previous build, the chassis must be booted with the copy of the original configuration file. If this copy is not available, then the chassis will need to be loaded as if it is a new chassis.
Files saved locally can be stored in the CompactFlash or a PCMCIA memory card on the SMC. Files that are saved to a remote network node can be transmitted through FTP or TFTP.
 
Saving the Configuration on the Chassis
These instructions assume that you are at the root prompt for the Exec mode:
[local]host_name#
To save your current configuration, enter the following command:
 
save configuration url [-redundant] [-noconfirm] [showsecrets] [verbose]
Command Syntax for Saving the Configuration
Specifies the path and name to which the configuration file is to be stored. url may refer to a local or a remote file. url must be entered using one of the following formats:
tftp://{ ipaddress | host_name [ :port# ] } [ /directory ] /file_name
ftp://[ username [ :pwd ] @ ] { ipaddress | host_name } [ :port# ] [ /directory ] /file_name
sftp://[ username [ :pwd ] @ ] { ipaddress | host_name } [ :port# ] [ /directory ] /file_name
/flash corresponds to the CompactFlash on the SMC.
/pcmcia1 corresponds to PCMCIA slot 1.
/pcmcia2 corresponds to PCMCIA slot 2.
ipaddress is the IP address of the network server.
host_name is the network server’s hostname.
port# is the network server’s logical port number. Defaults are:
Note: host_name can only be used if the networkconfig parameter is configured for DHCP and the DHCP server returns a valid nameserv er.dx
username is the username required to gain access to the server if necessary.
password is the password for the specified username if required.
/directory specifies the directory where the file is located if one exists.
/file_name specifies the name of the configuration file to be saved.
note_smallImportant: The -redundant keyword is only applicable when saving a configuration file to local devices. This command does not synchronize the local file system. If you have added, modified, or deleted other files or directories to or from a local device for the active SMC, you must synchronize the local file system on both SMCs.
 
To save a configuration file called system.cfg to a directory that was previously created called cfgfiles on the CompactFlash in the SMC, enter the following command:
save configuration /flash/cfgfiles/system.cfg
To save a configuration file called simple_ip.cfg to a directory called host_name_configs, using an FTP server with an IP address of 192.168.34.156, on which you have an account with a username of administrator and a password of secure, use the following command:
save configuration ftp://administrator:secure@192.168.34.156/host_name_configs/ simple_ip.cfg
To save a configuration file called init_config.cfg to the root directory of a TFTP server with a hostname of config_server, enter the following command:
save configuration tftp://config_server/init_config.cfg
 

Cisco Systems Inc.
Tel: 408-526-4000
Fax: 408-527-0883